Modular audio control surface

ABSTRACT

A user-configurable modular audio control surface comprises master modules for controlling global surface properties and channel modules for controlling one or more individual audio channels. The modules are disposed in a two-dimensional spatial arrangement such that any module can occupy a location within the control surface not occupied by another module. The modules are connected to each other and to external platforms hosting media applications and plug-ins via a network. Control surface users can interact with external applications via remote graphical user interfaces displayed on modules within the surface, and can automate multiple external applications using an automation system built into the surface. Automation line graphs and metadata for both internal and external applications are displayed over the corresponding waveform displays that can include audio ahead of a current playback location.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of, under 35 U.S.C.§120, and is a continuation of pending U.S. application Ser. No.13/836,456, filed Mar. 15, 2013, which is incorporated herein byreference.

BACKGROUND

In both live and offline audio editing environments, an audio controlsurface is a key item, since it provides the principal means by whichoperators can control the mixing of the various audio sources. As thenumber of input channels and range of audio processing functionsincreases, the size and cost of the control surface that is neededincreases. The number of channels in various deployed systems varieswidely, from only a handful in a hobbyist recording, to well over ahundred in a large live concert. In addition, the types of audioprocessing to be mixed into a final audio mix depend on the musicalsetting as well as on the nature of the user. Thus the type and numberof audio processing effects required may vary, from a handful of basicprocessing controls (e.g., EQ, compressor/limiter, expander, etc.) todozens of sophisticated digital signal processing effects, suchreverberation, delay, pitch correction, distortion, and modulation. Thismeans that control surface requirements can vary by well over an orderof magnitude between different users and applications. Over time, aparticular user may evolve from initially handling relatively small,simple mixes to requiring larger more elaborate ones. Such an evolutionwould preferably be accompanied by a corresponding increase in the scaleand processing capacity of the user's control surface.

Control surfaces represent a significant component of the capital costof an audio production studio, whether for an amateur, prosumer, orprofessional. As such, it is desirable for each user to equip themselveswith a control surface that is sufficient for, but not surplus to theirneeds, so that resources are not tied up in unused capacity.

Existing market solutions address various tiers of user requirements,each solution targeted to one of a handful of different user orapplication categories. In most cases, when a user's requirements changesignificantly, it is necessary to migrate to a different systementirely, possibly with a different user interface, with an associateddisruption and cost. There is therefore a need to address audio mixingneeds in a manner that is responsive to changing user requirements.

SUMMARY

In general, an audio control surface commensurate with a user's needs isconfigured from a range of standardized modules mounted in a frame andconnected to each other and to other audio processing devices, such as adigital audio workstation, by a network. Modules include those thatprovide traditional console controls, such as knobs, faders, touchsurfaces, and displays, as well as those that provide expanded and novelfunctionality. The control surface may simultaneously control theautomation of parameters of multiple externally hosted mediaapplications. Graphical user interfaces of external media applicationplug-ins may be displayed on displays within the control surface. Thecontrol surface may receive and display various kinds of data fromexternal media applications, including an audio waveform, an automationline graph, and metadata pertaining to audio tracks. Such data may bereceived and displayed in advance of real-time, i.e., in advance of acurrent playback time.

In general, in one aspect, an audio control surface comprises aplurality of modules, wherein each module comprises at least one of usercontrols for controlling properties of one or more media processingapplications and an output display for displaying one or more propertiesof the media processing applications, wherein the plurality of modulesare disposed in a two-dimensional spatial arrangement, and wherein eachof the modules is adapted to occupy one of a set of available locationswithin the control surface not occupied by another module, and whereineach module includes a CPU, random access memory, and a networkinterface that connects the module to a network.

Various embodiments include one or more of the following features. Atleast a part of the spatial arrangement conforms to a two-dimensionalrectangular grid. At least a part of the spatial arrangement comprisesmodules disposed along a curved grid. A given one of the modulesincludes a touch screen, and the user controls of the given modulecomprise a set of virtual controls implemented on the touch screen. Oneof the modules comprises a touchscreen interface configured with anexpandable touch control for controlling a given functional category,and expanding the touch control with a user-input touch gesture causes aset of virtual touch controls to be displayed, wherein each of the setof virtual controls is assigned to a function related to the givenfunctional category. A user is able to specify a spatial location for agiven one of the plurality of modules within the two-dimensionalarrangement of modules by: on a display of a designated module of thecontrol surface, positioning a graphical representation of the givenmodule on a two-dimensional graphical representation of the controlsurface in accordance with the location of the given module withincontrol surface; and in response to a request output by the designatedmodule, adjusting a control on the given one of the control surfacemodules, thereby causing it to output information that identifies it tothe designated module, and wherein the designated module associates theidentifying information of the given module with its spatial location. Agiven control of the control surface is assigned to controlfunctionality provided by one of a plurality of media applications, andeach of the plurality of media applications is hosted by a differentcomputer-based platform connected to the audio control surface via thenetwork. A user interface of a plug-in operating with a mediaapplication hosted on a platform external to the control surface and incommunication with the audio control surface via the network isdisplayed on a display of a designated module of the control surface.One or more physical controls in physical proximity to the display ofthe designated module are assigned to control functions of the plug-in.The audio control surface receives a graphical audio waveformrepresentation of an audio track from a media application external tothe audio control surface and in communication with the audio controlsurface via the network, and displays the graphical audio waveform on adisplay of a designated module of the control surface. During playing ofthe audio track by the media application, the audio control surfacereceives the graphical audio waveform representation of the audio trackcorresponding to temporal locations in the audio track in advance of acurrent playback temporal location in the audio track, and the audiocontrol surface displays the graphical audio waveform corresponding totemporal locations before and after the current playback time of theaudio track. The audio control surface receives automation informationfrom the media application and displays a graphical representation ofthe automation on the display of the designated module of the controlsurface such that the displayed automation information is temporallyaligned with the displayed graphical audio waveform representation ofthe audio track. The audio control surface receives metadata pertainingto a clip of an audio track that is represented by the graphical audiowaveform, and the audio control surface displays the metadata inassociation with the graphical audio waveform. During playback of theclip, the metadata pertaining to the clip is received by the audiocontrol surface in advance of a current playback time of the clip, andthe audio control surface displays the graphical representation of thewaveform and its metadata for a temporal interval spanning times beforeand after the current playback time of the clip. The control surfacereceives automation information from a media application hosted on aplatform external to the control surface, and displays a graphicalrepresentation of the automation on the display of a designated moduleof the control surface. The automation information pertains to an audioclip, and wherein during playback of the clip by the media application,the graphical representation of the automation information spanstemporal locations within the clip before and after a current playbacktime. The control surface receives metadata pertaining to a clip of anaudio track from a media application hosted on a platform external tothe control surface, and displays at least one of a graphical andtextual representation of the metadata. During playback of the clip bythe media application, the displayed representation of the metadatapertains to temporal locations within the clip spanning a currentplayback time. The audio control surface includes an internal automationsystem capable of automating one or more media applications hosted on aplatform external to the audio control surface. A user is able to recordand play back automation of a selected function of one of the pluralityof media applications, wherein the selected function is assigned to acontrol of one of the modules of the audio control surface.

In general, in another aspect, a module includes: a CPU; a random accessmemory connected to the CPU; a network interface for connecting themodule to a network; user controls for controlling properties of one ormore media processing applications and/or an output display fordisplaying one or more properties of the media processing applications;wherein the module is insertable into an audio control surface at anyone of a plurality of physical locations within the control surface, andthe plurality of physical locations are disposed in a two-dimensionalarrangement.

Various embodiments include one or more of the following features. Thetwo-dimensional arrangement includes at least one of a rectangular grid,a curved grid, and an irregular two-dimensional arrangement. The moduleis adapted to: receive via the network interface audio track data from amedia processing application hosted on a platform external to the audiocontrol surface during playback of the audio track by the mediaprocessing application; and output a representation of the audio trackdata on the display, wherein the output is based at least in part on acurrent playback location of the audio track by the media processingapplication.

In general, in a further aspect, a control surface module includes: aCPU; a random access memory connected to the CPU; a network interfacefor connecting the module to a network; user controls for controllingproperties of one or more media processing applications; an outputdisplay for displaying one or more properties of the media processingapplications; wherein the module is insertable into an audio controlsurface at any one of a plurality of physical locations within thecontrol surface, and wherein the module is adapted to: receive via thenetwork interface audio track data from a media processing applicationhosted on a platform external to the audio control surface duringplayback of the audio track by the media processing application; andoutput a representation of the audio track data on the display, whereinthe output is based at least in part on a current playback location ofthe audio track by the media processing application.

In general, in an additional aspect, an audio control surface includesuser controls for controlling properties of one or more media processingapplications hosted on one or more platforms external to the audiocontrol surface and an output display for displaying one or moreproperties of the media processing applications. The audio controlsurface receives information from the one or more media applicationswhich it displays on the output display. During playback of one or moreaudio tracks by one of the media processing applications, informationpertaining to the audio tracks is displayed in a manner that is based atleast in part on a current playback time of the audio tracks. Thedisplayed information includes one or more of an automation line graphpertaining to a parameter that is automated on one of the mediaprocessing applications; an audio waveform corresponding to an audiotrack being played back; and metadata associated with the audio track.The information is displayed for temporal locations within the audiobeing played back that span locations before and after a currentplayback time of the audio.

In general, in still another aspect, an audio control surface comprises:user controls for controlling properties of one or more media processingapplications; an output display for displaying one or more properties ofthe media processing applications; and an internal automation system,wherein the automation system is capable of automating a plurality ofmedia applications hosted on one or more platforms external to the audiocontrol surface.

In general, in another aspect, an audio control surface comprises: usercontrols for controlling properties of one or more media processingapplications; an output display for displaying one or more properties ofthe media processing applications; and wherein a user interface of aplug-in operating with a media application hosted on a platform externalto the control surface and in communication with the audio controlsurface via a network is displayed on the output display.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a frame of a modular control surface.

FIG. 2 illustrates a two-dimensional arrangement of modules in a modularcontrol surface.

FIG. 3 illustrates a curved two-dimensional arrangement of modules in amodular control surface.

FIG. 4A illustrates a user interface for identifying physical locationsof modules in a modular control surface.

FIG. 4B illustrates a user interface for identifying physical locationsof display modules in a modular control surface.

FIG. 5 is a high level diagram of a master touch module of a modularcontrol surface.

FIG. 6 is a high level diagram of a master automation module of amodular control surface.

FIG. 7 illustrates a channel knob module of a modular control surface.

FIG. 8 illustrates a top view of a column of knobs in the moduleillustrated in FIG. 7.

FIG. 9 illustrates a channel fader module of a modular control surface.

FIG. 10 illustrates a channel processing module of a modular controlsurface.

FIG. 11 illustrates a channel display module of a modular controlsurface.

FIG. 12 is a high level block diagram showing data communicationpathways among modules of the control surface and between the modularcontrol surface and external media applications.

FIG. 13 is a diagram illustrating a display of a graphical userinterface of an external media application plug-in on a display of amodular control surface.

FIG. 14 is diagram illustrating a display within a module of a modularcontrol surface of automation line curves superposed on an audiowaveform representation of the corresponding automated audio track.

FIG. 15 illustrates a display of a module of a modular control surfaceshowing audio waveforms, automation line curves, and metadata for audiotracks and clips received from an external digital audio workstation.

FIG. 16 is a high level process flow diagram illustrating automation ofmultiple external applications by an automation system within a modularcontrol surface.

FIG. 17 is a high level process flow diagram showing flow of informationduring automation of two external applications by an automation systemof a modular control surface.

DETAILED DESCRIPTION

As used herein, a digital audio workstation (DAW) refers to an audioapplication implemented on a computer, such as a personal computer,mobile device, touch pad, or other device that includes a CPU, memory,display, and input devices. DAW functionality includes, but it notlimited to the ability to record and play back more than one channel ofaudio and mix the channels together. A DAW may be implemented on adedicated device connected to a control surface that mediates the userinterface. DAWs may also include non-linear editing functionality, auser interface displaying a timeline that provides a temporalrepresentation of an audio clip, and the ability to cause audioprocessing to be performed on an audio signal. Such processing may beperformed either by the same platform that hosts the DAW, or anothersystem such as an audio processing engine that may be provisioned withdigital signal processors (DSPs).

As used herein, an audio processing engine refers to a system thatperforms audio signal processing so as to mix audio signals together andapply various audio corrections, enhancements and effects. The mixingfunction may be implemented on a physically distinct component of theaudio processing engine referred to as a mix engine. The audioprocessing engine may be located within an audio control surface orexternal to it, for example in a room that is sound-isolated from arecording studio.

As used herein, an audio control surface refers to a human interfacedevice used for controlling media applications, including audioapplications such as a DAW, a DAW's various plug-ins, and an audioprocessing engine. An audio control surface includes user controls, suchas faders, knobs, and switches, and may also include audio processing,audio input and output hardware, and mixing capabilities. An audiocontrol surface may also be used for controlling certain videoapplications, such as a non-linear video editing system.

Traditional audio control surfaces include banks of sliders and knobsthat are laid out in a configuration determined by the manufacturer. Thevarious sets of controls are hard-wired into the system, typically bothin terms of the integration of the physical controls into the controlsurface body, as well as in terms of the electrical connections behindthe surface. Typical control surfaces offer physical control of 8 to 32channels at a time via banks of faders and knobs. Channel capacity maybe expanded by software means, such as by assigning different sets ofchannels to the available hardware, as described, for example, in U.S.Patent Publication 2010/0266147, entitled “System and Method for AudioMixing,” which is wholly incorporated herein by reference. Physicalexpansion usually requires extending the length of the control surfaceby linear expansion, or completely replacing the control surface with amodel featuring a larger number of channels.

We describe herein a modular control surface system that addresses thescalability and customizability limitations associated with existingcontrol surfaces. The system enables a control surface to be configuredfrom modules arranged in two dimensions within a frame. The frame housesthe modules, providing mechanical support and allowing for thepositioning of inserted modules in a desired position, orientation, andheight. FIG. 1 is a diagram of an exemplary free-standing frame 100 withlegs. The frame defines the perimeter of the control surface, and mayinclude internal subdivisions within which individual modules areplaced, such as rectangular buckets 102, 104, 106, 108, 110. In theillustrated framework five rectangular buckets are arranged adjacent toeach other in a linear array. One or more modules can be housed withineach bucket. Unused spaces may be covered by filler panels 112.

In contrast to control surface systems that scale sideways in incrementsof 8, 12, or 16 faders, the system described here may be scaled inincrements of 8 faders, and may be scaled not only sideways, but also ina vertical manner, up and down what is conventionally termed a channelstrip. This facilitates customization to a user's needs since a userdoes not have to acquire more knobs than necessary if it is onlyadditional faders that are needed, or vice-versa.

A rectangular grid arrangement is illustrated in FIG. 2, in which thevarious modules of the control surface populate slots in a rectangulartwo-dimensional arrangement. The modular design enables a particularuser to select the modules needed, and add more modules as needed. Frame202 is sized to accommodate a user's current needs, as well as allowscope for future expansion. Once the length exceeds a certain value,such as a length of eight buckets in a row (as illustrated in theexample shown in FIG. 2), a supporting pair of legs are added to themiddle of the frame. Desktop frames without legs may also be used.Individual slots may be one of several standard sizes, or custom,configured to accommodate the desired modules. FIG. 2 illustrates aconfiguration that incorporates master touch module 204, masterautomation module 206, channel display module 208, channel knob module210, channel fader module 212, and channel processing module 214.

Each slot is provided with power sockets (e.g., low voltage DC powerdistributed from a single control surface power supply) and sockets toconnect to a standard network, such as Ethernet. The modules connect toeach other, to an audio mixing engine, and optionally to other computersand devices via a standard network interface that is included withineach of the modules.

The placement of each individual module within the grid may be selectedby the user. In general, the layout is chosen to optimize the ergonomicsand to conform to existing control surface layout conventions with whichthe user may be familiar. Since the modules connect with each other viaa network interface, and the framework provides standard sizes foraccommodating modules, in principle each of the modules can be placed inany location within the frame that is not occupied by another module. Inpractice, it may be desirable to subdivide the control surface frameand/or buckets into module locations having more than one standard size,so as to facilitate adherence to existing conventional layouts and toaccommodate modules that have different sizes. Non-rectilineargeometries for module placement on the surface may also be used, such asan arrangement of modules along an arc around the user. FIG. 3illustrates a configuration in which the modules are organized alongelliptical arcs 302, 304 centered on user 306. Such arcs may becircular, elliptical, or have other curved geometries.

When acquiring a control surface, a user's choice has hitherto beenlimited to one of a handful of standard surface models, each of whichmight be either under-specified or over-specified for that user. Acommon situation that results is that users are forced into acquiringmore than they need, which not only gives them an over-large, perhapsoverly complicated surface, but also wastes funds. The modular design ofthe described control surface enables a user to purchase a controlsurface that matches his needs, and is able to scale up or down as needschange. For example, as the number of input channels being handledincreases, it may be advantageous to equip a control surface with alarger set of channel modules. The configuration illustrated in FIG. 2includes 7 Channel Fader Modules, each of which is able to control 8channels, thereby allowing for the control of 56 channels without theneed to switch input channel assignments. In a situation where, forexample, 120 channels are being mixed, more channel modules are added tothe surface. These are inserted into empty locations within the existingframe, or accommodated by lengthening the control surface frame toprovide more locations to house the modules. The user is able toconfigure the surface to handle a greater number of channels by addingfader, knob, processing, and display modules in almost any combination.

In addition to the interchangeability facilitated by the standardphysical dimensions of the various control surface modules, the modulardesign is supported by the common network protocol that the modules useto communicate with each other, as well as with external platformshosting various media applications, such as DAWs, audio input/outputdevices that incorporate an audio mixer, controls for speaker arrays,such as in public address systems, and video editing applications. Thecommunication is implemented by a network connecting the modules to eachother and to external applications. In various embodiments the networkis a wired network or a wireless network, or a combination of wired andwireless networks. For example, the network implementing thecommunication internal to the control surface may of a first type, e.g.,wired, and the network connecting the control surface to external mediaapplications may be of a second type, e.g., wireless.

When initially populating a modular control surface with modules, orwhen adding, removing, or rearranging modules, a module configurationprogram is run on a master module of the surface, such as the mastertouch module, or on an external computer. In some embodiments theconfiguration program runs on a platform external to the controlsurface. The program enables the user to create a diagrammatic pictureof the current module layout on the module display. An exemplary userinterface is illustrated in FIGS. 4A and 4B. The user initiallyspecifies the number of module rows (or arcs in a curved geometry) andcolumns (or radial divisions) on the control surface, and theconfiguration program draws grid 402 with the specified number of rowsand columns, as shown in FIG. 4A. The program displays menu 404, whichshows icons of available control surface modules, such as master touchmodule icon 406. The user populates the diagrammatic representation ofthe physical control surface by selecting icons that correspond to thephysical modules present in the control surface from menu 404, andplacing them into the locations in diagrammatic representation 402 thatcorrespond to their physical locations in the surface. For example, asshown in FIG. 4A, the user places master touch module icon 408 into thecentral column of grid 402 to indicate a physical master touch modulelocated in the central bucket of the physical control surface in thesecond location from the bottom. Each of the module icons placed intothe diagrammatic representation is then highlighted in turn, and theuser is invited to touch a control on the physical module correspondingto the highlighted module icon. In response, the module then sendsidentification information, such as its MAC address, over the network,thus tying its location to its address, and making this available to thecontrol surface modules and external platforms on the network. Formodules that have no input controls, such as a channel display module,each of the physical channel display modules displays a uniqueidentifier, e.g., a number that uniquely identifies it to the controlsurface master module, e.g., a designated master touch module. At thesame time, a set of channel display module icons showing each of thesame unique identifiers is displayed by the module configurationprogram, as shown in FIG. 4B, 410. The user then identifies the physicallocations of the channel display modules to the system by selecting theicons that have the identifiers corresponding to those displayed on thephysical modules (e.g., 8, 4, 15), and dragging the icons to thelocations in the diagrammatic representation corresponding to each oftheir respective physical locations (e.g., locations 412, 414, and 416).

Master modules are used to control global properties of the controlsurface, such as applying a control to all of the channels being mixed,as well as selectable individual channels. Touch and physical controlsmay be assigned super-channel functionality, channel scrolling, layouts,tracks, monitoring, automation, and metering functions. A master touchmodule illustrated diagrammatically in FIG. 5, comprises two main parts.An upper part comprises a large (e.g., 12-inch) touchscreen surface 502,which implements a programmable variety of touch controls andinformation displays for the user. During setup, it is used to controlvarious groups of channels and/or individual channels. A lower part ofthe master touch module provides various physical controls including,for example, dedicated knobs 504, knobs 506 for monitoring controls,sets of soft keys 508 with associated displays (e.g., LCD) 510 for softkey labels, and a section for control of global system functionality,parameters, and settings. Also provided are various global controls(lower left), comprising such functions as channel settings, channelpaging, mute, solo, etc.

The user interface provided on touchscreen 502 includes hierarchicalbutton controls in which certain functions contain a set of relatedfunctions. For example, a user may expand box 512 using a touch gesturesuch as sliding two fingers apart in the vicinity of the box, therebycausing a set of buttons for controlling functions related to thecategory of functions of box 512 to be displayed. Thus if box 512controls the category of inserts, expansion brings up a set of effectfunctions such as modulations, EQ, dynamics, and reverbs. A pinchinggesture collapses the inserts back into a single box.

In the layout described in FIG. 5, large touchscreen 502 includes ascrollable list of functions, together with a display area forimplementing the controls for a user-selected function. In theillustration, the EQ function has been selected for the channel labeled“French Horns 2,” using the square-shaped touch buttons (512), and EQtouch controls are displayed in graphical form. A further set of touchcontrols is provided on large touchscreen 502 to control various userpreferences for the control surface such as meters, layouts, tracks,monitoring, automation, snapshots, and scenes.

A master automation module, such as the example illustrated in FIG. 6,provides transport and automation control, enabling users to controltheir synchronization system and have dedicated switches for time codeand transport-related operations. The module includes shuttle wheel 602,fader 604 that acts either as a master fader or an attention fader,various sets of soft keys, and number keypad section 606 with a dualtime code display.

Examples of channel module types that make up the described modularcontrol surface include the following. A channel knob module comprisesan 8-channel hardware module that is four knobs deep and allows a userto control up to 32 simultaneous knob values for processing on a digitalaudio workstation or on an audio processing engine. FIG. 7 illustratessuch a module, showing knobs with top-lighting to indicate the knobstatus, and displays, such as LCDs or OLEDs for indicating the knobfunction and value, as well as automation states. Additional detail ofthe top panel descriptions in the channel knob module is shown in FIG.8, which shows a column of four knobs. Knob 802 includes display (e.g.,LCD or OLED) 804 for showing parameter values, and select buttons 806. Achannel fader module comprises a set of eight motorized faders, allowingusers to control up to eight simultaneous DAW tracks or dedicated audioprocessing engine channels. FIG. 9 illustrates an exemplary channelfader module illustrating both the physical faders (e.g., fader 902) aswell displays (e.g., OLED display 904) for showing meters, channel andswap names, automation state, and menu commands, and mute and solobuttons 906).

A channel processing module comprises an eight-channel hardware moduleand the function control switches for a channel strip. Morespecifically, it enables a user to select the functions to be controlledby the knobs of a channel module, such as a channel knob module. Anexemplary channel processing module is illustrated in FIG. 10, showingeight sets of function selector buttons 1002. The functions control oneknob function per channel, or alternatively up to eight simultaneousknob values for a single channel. For example, in one application, thevarious values of an EQ for a single selected channel can be distributedacross all eight knobs of a channel processing module. The functionselector buttons may also be used to select a function for knob 1004,when more than one control for a channel is not available or needed.

A channel display module includes a hardware display (e.g., a wide viewangle TFT display) for eight channels, enabling users to view audiometers, routing information, function graphs, and other data. In onetypical configuration, the channel display module is mounted above otherchannel modules, forming part of a channel strip. FIG. 11 is adiagrammatic illustration of a channel display module displaying a rowof channel audio signal meters for each of eight channels (1102), and arow of line graphs (1104) showing one or more of a number of signalproperties, such as an EQ curve, a compression curve, or a pan location.Routing of inputs and outputs are indicated in bottom row 1106, withhighlighted numbers indicating the output channels to which each channelis routed.

Users may wish to add functionality, such as audio processing effects,by installing a plug-in on the control surface or on a DAW or mixingengine associated with the control surface. Since a control surface canbe quite large, in some cases over 30 feet in length, the separation ofa DAW or mix engine display monitor from the control surface virtual andphysical controls assigned to the plug-in can be quite considerable.This can result in awkward ergonomics, with the user reaching over tocontrols at one end of a control surface, while looking at a display atthe other end, or even needing to physically move to a new position tobe able to manipulate the controls and see the plug-in user interface.

In the described modular control surface, the graphical user interface(GUI) of a plug-in is routed to control surface displays that are closeto the physical controls assigned to manipulate the plug-in parameters.In effect, both the user input controls and the user-visible output ofthe plug-in are assigned to a convenient location on the controlsurface, without regard to the type and location of the platform that isrunning the application. FIG. 12 illustrates this point, by showingcontrol surface 1202 having multiple modules (e.g., module 1204) allconnected via network 1206 using a standard protocol such as Ethernet,to each other and to external platforms, such as DAWs 1208 and 1210, aswell as mixing engine 1212. The routing of the plug-in user interface tophysical controls and touchscreen controls for input and a display foroutput is independent of the platform hosting the plug-in, which may bea DAW (1208, 1210) or a mixing engine (1212), even when the externalapplications and the control surface module are running differentoperating systems. As shown in FIG. 13, the plug-in GUI may be displayedboth on the display of the system hosting the plug-in (1302) as well ason a display within module 1304 of the described modular controlsurface. As an example of cross-platform compatibility, system 1302 maybe running MICROSOFT® WINDOWS® or MAC OS® and control surface module maybe running the LINUX operating system. The plug-in GUI may be displayedas a window floating on top of existing information that is beingpresented on the control surface. In one implementation, the displaydrawing calls from the external application are intercepted, routed tothe control surface and replicated under a new operating system. Inanother implementation, a cross-platform drawing library is used to drawboth on application host 1302 and on control surface module 1304. Forplug-ins or other applications with GUIs featuring touch inputs,remoting the interface to the control surface may include routing thedisplay outputs to the control surface display, and assigning the inputsto physical controls in proximity to the control surface display. In amore complete implementation, both the output displays and the touchinput controls are remoted to the control surface touchscreen interface.In a further implementation, the GUI bit map that is output to thedisplay of the plug-in host system is routed to the control surface fordisplay as well. This is achieved by reading out the contents of thehost system frame buffer, or by intercepting the data as it is beingwritten to the frame buffer, and then sending it to the control surfacefor display. Control surface modules that are suitable for displaying aplug-in GUI include a channel display module, especially when a plug-inis being applied only to an individual channel, and a master touchmodule.

The assignment of the various physical controls of a control surface toparameters of the DAWs and other external applications is performed byeither or both of pre-assignment by the system and assignment by theuser. The assignment may be performed down to a granularity ofindividual faders, knobs, and switches. Pre-assignment of the functionsof the surface controls is established between the control surface andthe external media applications by means of an industry standard networkprotocol. An example of such a protocol is EUCON™, available from Avid®Technology of Burlington, Mass., which supports tagging of externalapplication parameters that enables the surface logic to map thoseparameters intelligently to suitable surface controls. User assignmentof physical controls to a particular application external to the controlsurface is managed via a user interface hosted by logic within thecontrol surface, for example within a master touch module. Informationas to the physical location of each module, and each control within thatmodule, is distributed across all the platforms running the externalapplications as well as the module hosting the control assignments. Theassignment information is also available to other control surfacemodules, which provides some redundancy in case of failure of a mastermodule or an external platform. At any one time, any given control iscontrolled by a single application, and it may then be directlycontrolled from the external application. Once assigned, internalcommunication based on TCP/IP is used to send control movement messagesbetween each module and the control surface logic. In variousimplementations, the surface logic is distributed, and control movementmessages are broadcast to all the external applications.

Embedding third party graphical content within the control surfacedisplays enables users to experience the full richness of the originalplug-in interface, both with respect to plug-in functionality as well asthe graphical look and feel and branding of the plug-in. In other words,the system does not require the plug-in functionality to be abridged orsimplified when accessed from the control surface rather than from thesystem hosting the plug-in.

Many audio and video applications can record and play back movements ofcontrol parameters that vary with temporal location within a giventime-based media component. For example, the volume, EQ, compression,limiter, and stereo pan of an audio track may be adjusted duringplayback. These adjustments are recorded and time-stamped as they occur.During playback, the application responsible for the adjusted controlreproduces the recorded adjustment, enabling play back without theoperator having to touch the controls any further. This is calledautomation, and it can be used for any type of control, includingfaders, switches (e.g., mute), and knobs.

Automation dramatically improves workflow. Complex musical compositionsand soundtracks with hundreds or even thousands of parameter changes canbe realized because the sound engineer can work on a few parameters at atime, while an automation system faithfully plays back all the parameterchanges.

In order to provide the user with a visual representation of automationsettings, a line graph representing the time-varying value of theautomated parameter is displayed. For example, in a two-dimensionalgraph, the horizontal (x) axis may represent time, and the vertical (y)axis represents the value of the parameter. Applications that hostautomation typically show this line graph on a display of the platformhosting the application. As discussed above, control surfaces forcomplex mixing tasks are often long, and a user may not be able to viewthe automation line graph on the display of a DAW hosting the automationwhile at the same time being positioned in front of the control surfacewith access to the controls needed. This ergonomic and workflow problemis addressed by embodiments of the described modular control surfacethat enable an automation line graph from external applications andplug-ins hosted on platforms outside the control surface to be displayedon a monitor within the control surface, such as a master touch modulescreen or a channel display module screen. The automation line graph maybe superimposed over an audio waveform, which helps the user gauge theaccuracy of the automation timing, and the nature of the automationcurves. FIG. 14 illustrates display 1402 of control surface module 1404,with waveform/automation line graph display area 1406. In the exampleillustrated in FIG. 14, display area 1406 comprises eight graphs, onefor each of eight channels, such as graph 1408. Each graph shows anautomation line graph, such as automation line graph 1410, superposed onthat channel's audio wave form 1412, which is a visual representation ofaudio signal amplitude (e.g., in decibels) plotted against time. In theexample shown, the automation line graph represents fader gain level indecibels, plotted against time. Other parameters that have beenautomated may be shown as additional lines on the same graph or onseparate graphs. Automation line curves for internally recorded andplayed back automation may also be displayed, either as another linegraph on a graph showing externally driven automation, or on a separategraph.

During mixing of pre-recorded audio, a user may wish to anticipatecertain audio events so as to be able to alter the mix before theseevents are played. For example, when mixing a track from a movie soundtrack, the user may want to reduce the volume of a loud event such as adoor slamming or a gunshot so that it does not overpower other sounds orunduly shock the viewer. To enable anticipatory mixing, upon requestfrom the user, waveform and automation information is sent to thecontrol surface in advance of real time. For a viewable time span of 30seconds, a typical split would be 10 seconds of past data and 20 secondsof future data. The waveform information is a pre-rendered graphic ofthe audio sample it represents, i.e., the displayed waveform ispre-generated directly from the audio sample. This contrasts withsystems that generate the waveform from a recording of meter values,which produces a less accurate representation.

In addition to receiving waveform and automation information, thesurface may also receive metadata from external applications thatpertain to the displayed audio signal and its automation. An example ofmetadata display in association with the automation line graph and thewaveform display is shown in FIG. 15. In this example, which involvescontrolling a DAW, time is plotted vertically in the displayed graphs,with waveform/automation line graphs displayed for each of four audiotracks 1502, 1504, 1506, and 1508. As used herein, the term track refersto an audio track of a DAW, and an audio clip refers to a portion of anaudio track, e.g., defined by a temporal range, or may also refer to anentire audio track. Each track is assigned to one or more channels onthe control surface. Automation line graph 1510 shows fader volume indecibels, superposed on audio signal waveform 1512, with which it istemporally synchronized. The display includes the following metadata:track name 1514; track number 1516; name of current clip being played1518 in a particular track; name of the next clip to be played 1520; andindication 1522 as to whether the track is locked to the correspondingphysical strip, i.e., the column of controls that may extend acrossseveral control surface modules that is assigned to control the track.The displayed portion of track 1508 includes parts of two clips 1524 and1526, which are distinguished on the display by distinct colors orshading. The display also shows playhead (or Now Line) 1528,corresponding to the current temporal location in the displayed tracksof playback. In the examples mentioned above, a gunshot or a door slamsound may be described as such in the clip name metadata. Other metadatamay be tied to a transition sequence, such as a scene change for amovie, e.g., “fade to outdoor scene.” Such metadata is sent to thesurface to accompany both real-time and advance waveform and automationline graph information. The metadata is displayed in association withthe waveform and automation line graph. To summarize: the automationline graph display may include three kinds of information: (1) theautomation line graph itself, (2) the audio waveform, and (3) metadatapertaining to the audio; the information originates from either or bothof applications running externally to the control surface, such as onDAW plug-ins, and from applications that may be running internally onthe control surface. Seamless receipt and display of information frommultiple external and internal applications is facilitated by thestandard network interface and protocol between the control surfacemodules and the external applications.

In various embodiments and as illustrated in FIG. 16, the describedcontrol surface 1602 includes its own automation system 1604 that isable to record and play back automation for multiple applications (1606,1608, and 1610) simultaneously. For example, the volume on a first trackof a DAW application may be controlled by automation for a first faderon the control surface, while a video application parameter such as avideo audio track level, color correction, hue saturation parameter, orwipe speed of a transition, may be controlled by automation of a secondfader.

FIG. 17 is a block diagram of control surface 1702 and computers 1704and 1706 that host media editing and processing applications (such as aDAW or a video editor) showing more details of the automation system(1708) within the control surface, and the manner in which it operateswith the other components of the control surface and with the externalmedia applications.

The user enables the recording of automation by pressing an audio playkey to start playback, and then initiates the recording of automation ofone or more controls by using one of a number of means provided on thecontrol surface, such as toggling a button associated with a control ortouching the control. This causes automation recorder 1710 to startrecording the changes made by the user to the control, which are thenstored in automation database 1712. The user inputs the changes viaphysical controls 1714 on the surface and/or virtual controls 1716 on atouch screen within one of the control surface modules (e.g., mastertouch module). The corresponding parameter changes are sent to surfacelogic 1718, which interprets the raw physical or virtual switch pressesand fader moves, converting them into corresponding messages over thenetwork using a communication protocol, such as EUCON. The messages arealso routed to automation recorder 1710 for storing in automationdatabase 1712, and sent from the surface to the one or more computers(1704, 1706) each hosting an application (1720, 1722 respectively)assigned to the control that has been adjusted. Examples of commerciallyavailable DAWs include PRO TOOLS® from Avid Technology, Inc., LOGIC®from Apple® Computer, Inc. and CUBASE® from Steinberg®. The applicationsto which the control surface messages are sent could be other types ofmedia applications, including video editing applications such as MEDIACOMPOSER® and FINAL CUT PRO®. Incoming message dispatchers 1724, 1726receive the messages from surface logic 1718, and forward parameterchange callbacks to applications 1720 and 1722. In response, the DAWsapply the parameter changes to audio processing within the DAW, andissue parameter set calls that are routed to outgoing message senders1732, 1734, and then sent over the network back to the control surface.Applications 1720 and 1722 also move graphical controls (e.g., faders,knobs, etc.) corresponding to the changed parameters on their displaysin alignment with the surface controls. In certain circumstances, thisposition may be different from the physical position last input on thecontrol surface by a user, such as if the user moves the control outsidea range supported by the external application. Audio inputs fromapplications 1720 and 1722 are shown at 1728 and 1730 respectively, andaudio outputs are shown at 1736 and 1738 respectively.

To play back the automation, the user starts playback with a predefinedaction, such pressing the audio play key, which sends a control signalto automation player 1740 to start playback. The player retrieves therecorded automation commands from automation database 1712, and playsthem out via the surface logic 1718, which then acts upon controls 1714and 1716, as well as applications 1720 and 1722. In order to reducevulnerability to network latency during playback, a block of automationdata may be transferred from the surface to the applications in advanceof them being required for playback and stored in a local cache, and arethen available locally (i.e., with no latency) during playback.

Implementation of the various software components of the describedmodular control surface may be on a single platform or distributedacross more than one platform. For example, surface logic 1718, which isshown as a part of control surface 1702 in FIG. 17, may be implementedon a CPU in the control surface, or on a CPU in a workstation computerhosting a connected DAW, or distributed across both the control surfaceCPU and the workstation CPU. When data is communicated between modulesor between platforms, the standard network protocol, such as ETHERNET isadopted. By contrast, if control surface functions are implementedwithin a single module of the control surface, communication among thesefunctions may use direct internal message passing, without the use ofthe external network protocol.

The various components of the system described herein may be implementedas a computer program using a general-purpose computer system. Such acomputer system typically includes a main unit connected to both anoutput device that displays information to a user and an input devicethat receives input from a user. The main unit generally includes aprocessor connected to a memory system via an interconnection mechanism.The input device and output device also are connected to the processorand memory system via the interconnection mechanism.

One or more output devices may be connected to the computer system.Example output devices include, but are not limited to. LCD, plasmadisplays, OLEDs, various stereoscopic displays including displaysrequiring viewer glasses and glasses-free displays, cathode ray tubes,video projection systems and other video output devices, printers,devices for communicating over a low or high bandwidth network,including network interface devices, cable modems, and storage devicessuch as disk or tape. One or more input devices may be connected to thecomputer system. Example input devices include, but are not limited to,a keyboard, keypad, track ball, mouse, pen and tablet, touchscreen,camera, communication device, and data input devices. The invention isnot limited to the particular input or output devices used incombination with the computer system or to those described herein.

The computer system may be a general purpose computer system which isprogrammable using a computer programming language, a scripting languageor even assembly language. The computer system may also be speciallyprogrammed, special purpose hardware. In a general-purpose computersystem, the processor is typically a commercially available processor.The general-purpose computer also typically has an operating system,which controls the execution of other computer programs and providesscheduling, debugging, input/output control, accounting, compilation,storage assignment, data management and memory management, andcommunication control and related services. The computer system may beconnected to a local network and/or to a wide area network, such as theInternet. The connected network may transfer to and from the computersystem program instructions for execution on the computer, media datasuch as video data, still image data, or audio data, metadata, reviewand approval information for a media composition, media annotations, andother data.

A memory system typically includes a computer readable medium. Themedium may be volatile or nonvolatile, writeable or nonwriteable, and/orrewriteable or not rewriteable. A memory system typically stores data inbinary form. Such data may define an application program to be executedby the microprocessor, or information stored on the disk to be processedby the application program. The invention is not limited to a particularmemory system. Time-based media may be stored on and input frommagnetic, optical, or solid state drives, which may include an array oflocal or network attached disks.

A system such as described herein may be implemented in software orhardware or firmware, or a combination of the three. The variouselements of the system, either individually or in combination may beimplemented as one or more computer program products in which computerprogram instructions are stored on a non-transitory computer readablemedium, for execution by a computer, or transferred to a computer systemvia a connected local area or wide area network. Various steps of aprocess may be performed by a computer executing such computer programinstructions. The computer system may be a multiprocessor computersystem or may include multiple computers connected over a computernetwork. The components described herein may be separate modules of acomputer program, or may be separate computer programs, which may beoperable on separate computers. The data produced by these componentsmay be stored in a memory system or transmitted between computersystems.

Having now described an example embodiment, it should be apparent tothose skilled in the art that the foregoing is merely illustrative andnot limiting, having been presented by way of example only. Numerousmodifications and other embodiments are within the scope of one ofordinary skill in the art and are contemplated as falling within thescope of the invention.

What is claimed is:
 1. A media control surface comprising: one or moremodules, wherein at least one of the one or more modules includes: anetwork interface that connects the module to a network; an outputdisplay for displaying properties of one or more media processingapplications hosted on one or more platforms external to the mediacontrol surface, wherein each of the one or more platforms is incommunication with the media control surface via the network; and anautomation system capable of automating the one or more media processingapplications, wherein automating a given one of the one or more mediaprocessing applications includes: at the automation system, receivingcontrol parameter adjustments via one or more input controls of themedia control surface, wherein the control parameter adjustments areapplied to the processing of media data by the given one of the one ormore media processing applications; recording the control parameteradjustments; and applying the recorded control parameter adjustmentswhile the media data is being played back.
 2. The audio control surfaceof claim 1, wherein a user is able to select a parameter of one of theone or more media processing applications, and following the selection,the automation system is capable of recording and playing backautomation of the selected parameter, wherein the selected parameter isassigned to an input control of one of the plurality of modules.
 3. Theaudio control surface of claim 1, wherein the automation systemtime-stamps and records adjustments of a selected control parameter whenthe adjustments are made.
 4. The audio control surface of claim 1,wherein the output display receives from the automation systemtime-based automation information for one or more of the one or moremedia processing applications and displays a graphical representation ofthe time-based automation information.
 5. The audio control surface ofclaim 1, wherein the output display: receives from the automation systemtime-based automation information a of media processing applicationhosted by the control surface; receives over the network time-basedautomation information for one or more of the one or more externallyhosted media processing applications; and displays on the output displaya graphical representation of the time-based information for both themedia processing application hosted by the control surface and the oneor more externally hosted media processing applications.
 6. The audiocontrol surface of claim 1, wherein: a first parameter of a given one ofthe one or more media processing applications is automated by theautomation system; the given one of the one or more externally hostedmedia processing applications includes a second automation system; and asecond parameter of the given one of the one or more externally hostedmedia processing applications is automated by the second automationsystem.
 7. The audio control surface of claim 6, wherein the outputdisplay receives automation information for the first and secondparameters, and displays a graphical representation of the automationinformation for the first and second parameters.
 8. The audio controlsurface of claim 1, wherein the audio control surface receives over thenetwork a graphical audio waveform representing audio data beingprocessed by one or more of the one or more media processingapplications, and displays the graphical audio waveform on the outputdisplay.
 9. The audio control surface of claim 1, wherein the audiocontrol surface receives over the network metadata pertaining to audiodata being processed by one of the one or more media processingapplications, and displays the metadata on the output display.
 10. Theaudio control surface of claim 9, wherein the audio data being processedby one of the one or more media processing applications corresponds toan audio clip.
 11. A media control surface module comprising: a CPU; arandom access memory connected to the CPU; a network interface forconnecting the module to a network; an output display for displayingproperties of one or more media processing applications hosted on one ormore platforms external to the audio control surface, wherein each ofthe one or more platforms is in communication with the audio controlsurface via the network; and an automation system, wherein theautomation system is capable of automating the one or more mediaprocessing applications, and wherein automating a given one of the mediaprocessing applications includes: at the automation system, receivingcontrol parameter adjustments via one or more input controls of themedia control surface, wherein the control parameter adjustments areapplied to the processing of media data by the given one of the mediaprocessing applications; recording the control parameter adjustments;and applying the recorded control parameter adjustments while the mediadata is being played back.
 12. The media control surface of claim 11,wherein during playback of the media data, the output display: receivesdata describing the recorded control parameter adjustments; and displaysa graphical representation of the control parameter adjustments.
 13. Amethod of automating one or more media processing applications, themethod comprising: receiving via one or more input controls of a mediacontrol surface adjustments of a set of control parameters forcontrolling media data, wherein the control parameter adjustments applyto parameters of one or more media processing applications hosted onplatforms external to the media control surface; and using an automationsystem hosted by the media control surface: recording the controlparameter adjustments; and applying the recorded control parameteradjustments to adjust values of the set of control parameters of theexternally hosted one or more media processing applications while themedia data is being played back.
 14. The method of claim 13, wherein themedia control surface includes an output display, and further comprisingduring playback of the media data: receiving at the output display datadescribing the recorded control parameter adjustments; and displaying onthe output display a graphical representation of the recorded controlparameter adjustments.
 15. The method of claim 13, wherein the mediacontrol surface includes an output display, and further comprisingduring playback of the media data: receiving at the output display agraphical audio waveform representing audio data being processed by oneof the one or more media processing applications; and displaying thegraphical audio waveform on the output display.
 16. The method of claim13, wherein the media control surface includes an output display, andfurther comprising during playback of the media data: receiving at theoutput display metadata pertaining to audio data being processed by theone or more media processing applications; and displaying the metadataon the output display.
 17. The method of claim 16, wherein the audiodata being processed comprises a clip of an audio track.
 18. The methodof claim 13, wherein the media data comprises a clip of an audio track.